MacWorld 1999 May/Macworld (1999-05).dmg/Serious Software/FlightCheck Collect 3.52 trial/FLIGHTCHECK® COLLECT! DEMO/FLIGHTCHECKÆ COLLECT! DEMO.rsrc/TEXT_152_ Fonts Category.txt

Text File | 1999-03-16 | 4KB | 29 lines

Fonts Category

The Fonts category offers you a way to ensure that the fonts used in your document are desirable, and is divided into Status, Type and Usage controls.

Status Controls
Check the Active box for FlightCheck to alert you when any font the document is using is not currently active in your System.

Check the Screen Font box to be alerted when any Screen Font the document is using cannot be located, meaning the font is neither active in the System nor can FlightCheck find the named font in the Fonts Database.

Check the Printer Font box for FlightCheck to alert you when any Printer Font file cannot be located. A missing printer font file will always force the printer to substitute the font with some default font (usually Courier).

Note that not all fonts require a companion printer font file and some fonts (such as TrueType®) have built-in printer instructions on how to draw the characters.

Type Controls
Check the TrueType‚Ñ¢ box for FlightCheck to alert you when any
font is of the type TrueType. Some output devices are incapable of handling TrueType fonts, and furthermore it is
a generally accepted fact that mixing fonts on a page (using Type 1 and TrueType) can cause some unexpected output problems.

Check the City/System Font box for FlightCheck to alert you when any font has a name that is associated with a city, such as Chicago, Geneva, Monaco, Charcoal, etc. The reason for this is that most “city” or System fonts are usually merely bitmap fonts and always print at a fairly low quality, thus they should be avoided.

Check the Multiple Masters box for FlightCheck to alert you when any font is of the type Multiple Masters.

Check the Non-Adobe® box to be alerted when any font is not an official Adobe font. With all due respect for other font manufacturers, many of whom create very high quality and fine-looking fonts, it is sometimes decided by certain designers to commit to all Adobe fonts to ensure output compatibility. It is a known fact that mixing different types of fonts on a page can lead to unwanted output problems. These kinds of issues can be avoided if a policy is set for the workflow that a document should always be created using only known versions of Adobe fonts (or for that matter, any one manufacturer’s fonts) which per the licensing agreement the Service Bureau will likewise own and therefore the expected output will be predictably safe.

Usage Controls
Check the Menu Styled box for FlightCheck to alert you when any font has been stylized via the application’s Style menu and the font contains no equivalent built-in style. This problem exists rather frequently. For example, if you select some text and choose “Bold” from the Style menu, but the font itself is incapable of printing in boldface, then even though the text appears bold on the screen, it will be printed as plain text on paper. Additionally, if the font can indeed support the style, its companion printer font file must also exist in order to achieve the desired style during printing. Therefore, FlightCheck will warn you if either the font cannot support the style, or the printer font cannot be found.

Check the Encoding box for FlightCheck to alert you when any font uses a Non-Standard Encoding. Not all printing devices are capable of printing all characters in a set and therefore certain characters may need to be “remapped”. This is normally based upon a standard encoding scheme, which could vary on different platforms. Therefore, this checkbox can be used to point out possible output conflicts.